Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Adjust rendering of backend module from fluid to fusion #61

Merged
merged 6 commits into from
Jan 16, 2023

Conversation

mficzel
Copy link
Member

@mficzel mficzel commented Jan 6, 2023

This change adjusts the rendering from fluid to fusion.

Additionally Packages can now add additional fields to the forms of taxonomies and vocabularies. To do this
the following steps are required.

  1. Extend the NodeTypes Sitegeist.Taxonomy:Taxonomy or Sitegeist.Taxonomy:Vocabulary in your package.
  2. Add tha path to your additional Root.fusion to the Setting in path Sitegeist.Taxonomy.backendModule.additionalFusionIncludePathes.
  3. In the fusion code define each field as prototype that accepts the props name plus taxon & defaultTaxon resp. vocabulary & defaultVocabulary.
  4. Register addtional prototypesNames by adding them to the Settings Sitegeist.Taxonomy.backendModule.additionalVocabularyFieldPrototypes or Sitegeist.Taxonomy.backendModule.additionalTaxonomyFieldPrototypes

Note: For the rendering of flash messages the following bugfix in Neos is needed: neos/neos-development-collection#3999

@mficzel mficzel force-pushed the feature/fusionRendering branch 2 times, most recently from 4d57cca to 5283e51 Compare January 10, 2023 09:48
@mficzel mficzel marked this pull request as ready for review January 10, 2023 09:48
composer.json Outdated Show resolved Hide resolved
@mficzel
Copy link
Member Author

mficzel commented Jan 13, 2023

@jonnitto thanks for the comments adjusted as suggested and even added a very basic extensibilty.

Packages can add additional fields to the forms of taxonomies and vocabularies. To do this the following steps are required.

1. Extend the NodeTypes `Sitegeist.Taxonomy:Taxonomy` or `Sitegeist.Taxonomy:Vocabulary` in your package.
2. Add a Views.yaml to your package and configure additional Fusion pathes to be loaded.
3. In the fusion code define each field as prototype that accepts the props `taxon` & `defaultTaxon` resp. `vocabulary` & `defaultVocabulary`.
4. Register those prototypes by adding them to the property `additionalFieldPrototypeNames` of the prototype `Sitegeist.Taxonomy:Form.Taxonomy` or `Sitegeist.Taxonomy:Form.Vocabulary`
@mficzel mficzel merged commit fbc1528 into master Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants